fix(BREV-2823): Remove hardcoded sfc locations#92
Merged
Conversation
stephahart
previously approved these changes
Feb 18, 2026
stephahart
reviewed
Feb 18, 2026
| } | ||
|
|
||
| // If the there is no available capacity, and skip it | ||
| // If the there is no available capacity, skip it |
Contributor
There was a problem hiding this comment.
This sentence still doesn't quite make sense 😆
… any region that's available (#91) * add richmond region to stable types * don't restrict which zones can be used, allow all zones
tylerfong
force-pushed
the
sfclocations
branch
from
0855ec7 to
824e406
Compare
theFong
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.